CloudSocket Roles #

CloudSocket Provider #

Runs an instance of CloudSocket and offers the service to the other parties.

Organization installing, executing and managing a CloudSocket instance on a given owned or rented (i.e. cloud-based) infrastructure under its own control.

A CloudSocket Provider is paid by the Customers, and pays the ExternalService Providers.

FHOSTER refers to CloudSocket Provider as 'Cloud Socket Instance Provider'

Business Process Modeller #

uses the graphical modelling interface to define busines processes

Organization using the CloudSocket Design Environment to create a Business Process model and populate the Marketplace of a CloudSocket Instance. Executable Business Providers may provide an implementation to such a Business Process Model.

In such a case, the CloudSocket provider may pay further royalty to the Business Process Modeller when an Executable Business Publisher is paid.

Executable Business Process Modell Publisher #

Provides executable processes; multiple EBPMs may match a single Business process.

Organization using the BPaaS Design Environment to create an Executable Business Process Models and populate the Marketplace of a CloudSocket Instance. The Cloud Socket Provider might pay a royalty to the EPP when one of its Executable Business Process Models is actually used by a Broker to deliver a Cloudlet to a Customer.

Open Question: are there multiple Brokers per CloudSocket Instance?

Business Process Operator #

User of CloudSocket in the sense that it specifies requirements and has the platform create a Cloudlet. Is the instance to be billed by the CloudSocket Provider.

Business Process User #

The actual person/set of persons interacting with the Business Process realised through the Cloudlet, e.g. a case worker in a personnal department. Very likely that this person belongs to the same institution as the operator.

External Service Provider\\ #

Organization installing, executing and managing a WS Instance on a given infrastructure under its own control. An External Service Provider autonomously defines a SLA for the External Service; He is responsible to fulfill such SLA, and is paid according to the usage of the External Service he provides.

FHOSTER refers to External Service Provider as 'Service Instance Provider'